COMMENT ⊗   VALID 00002 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	-------
C00009 ENDMK
C⊗;
-------
   That was message 2
Date: 14 JUL 1975 1113-PDT
From: WOLPERT
Subject: ILISP @ SUMEX
To:   FAUGHT

I HAVE PUT AN ENTIRELY NEW VERSION OF THE ILISP SYSTEM UP IN
<ILISP>.  NEW VERSION WILL BE UP AS <SUBSYS>ILISP AS SOON AS
THE POWERS THAT BE CHECK WITH THE USER COMMUNITY, IF ANY.
(DON'T ASK ME...I ANI'T THE BEAUROCRATIC TYPE).

IN THE MEANTIME, DON'T TRY TO LOAD ANYTHING INTO
SUBSYS VERSION...SUPPORT FILES ARE ALL FOR THE NEW VERSION
AND WILL GIVE PROBLEMS WITH THE OLD ONE.  

FILES FOR BOOTING MLISP ARE NOT THERE, BUT A NEW VERSION
OF MLISP IS.  IF YOU WANT THE BOOT FILES, WE CAN GET
THEM TO YOU LATER.  SUMEX IS HYPER ABOUT DISK SPACE AND
DOES NOT WANT SOURCES ON THE DISK...

IF THERE IS ANYTHING I CAN DO, LET ME KNOW.

TOM
-------
   That was message 3
Date: 15 JUL 1975 0904-PDT
From: COWER
Subject: PARRY
To:   FAUGHT

BILL, WOULD IT BE POSSIBLE TO GET A PARTIAL VERSION OF PARRY? WE NEED
ONE THAT DOES NOT HAVE THE STARTUP STUFF AT THE BEGINING OF IT AND
THAT DOES NOT PRINT THE ANGER, FEAR STUFF, AND THAT DOES PRINT NON-
VERBAL THINGS (LIKE SOCKING YOU IN THE NOSE, ETC). BUT IT MUST BE
ABLE TO DO ALL THESE THINGS WITHOUT ANY OF THE STARTUP JUNK. THIS IS
A PRIVATE THING WE WANT TO WORK ON DOWN HERE. IF IT CAN BE EASILY DONE
PLEASE SNDMSG TO ME. IF NOT, DON'T WORRY ABOUT IT...THANKS....RICH
-------
   That was message 4
Date: 15 JUL 1975 2142-PDT
From: NSMITH
Subject: GUEST policies
To:   faught, scott

	We should shortly have some documentation on GUEST
policies and will be notifying you about where your programs
should go and how.  Right now we are investigating ways to
provide security.  For example, blocking guests from getting
into the system proper by sophisticated use of LISP.  Ray
Carhart has put some protection in CONGEN and we hope to draw
up guidelines on how to do that for other LISP programs.  In
general an alias will be put on <GUEST> which runs the program
from another directory.  Currently the other directory involved
has been the project's directory like <MYCIN>, <PARRY>, etc.
We may set up a separate intermediate directory <GUESTSYS> where
we could keep a close eye on all these programs.  In any case,
it is the user which has restricted access to other directories.
The program itself will have access to whatever it needs.
Feel free to notify us of any comments you have on the situation.
There will be a new SUMEX staff member assigned to these concerns,
but I wanted to let you know the current status of the situation
since it came up in relation to the documentation for this ARPA
Handbook report.
	Nancy
-------
   That was message 5;  that was the last message

<- Exit and update old file MESSAGE.TXT;1 [Confirm] 
   Good-bye.